Adding troubleshooting information about Subresource Integrity digests.#1220
Conversation
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks! If you are contributing on behalf of someone else (eg your employer): the individual CLA is not sufficient - use https://developers.facebook.com/opensource/cla?type=company instead. Contact cla@fb.com if you have any questions. |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Can we generate this file by default? Like we generate |
|
The |
|
Sounds good, thanks! |
4 participants
Adding this section to the troubleshooting documentation:
Subresource integrity checks fail
Subresource Integrity digests are added to the build output files. For a particular scenario, these checks may fail when deployed. The files are built using
LFcharacters, but if your deployment uses a Git repository for deployment (like Azure web sites) and the Git repository is set up to translateLFcharacters intoCR/LFcharacters, then the checked out files will be different and the digests will be invalid.To fix this, just add a
.gitattributesfile to your deployment repository that will ensure the build files are not modified when checked out: